In order to perform static-analysis on Gecko we use the clang-tidy infrastructure, for this we a tool run-clang-tidy, that spawns multiple process in order for the analysis process to be faster. Unfortunately run-clang-tidy doesn't uses a write synchronization when it comes to dump output in the stdout of stderr, because of this many time we see that the outputs is interlaced with results from different files, thus making it less readable to human and also to machine. In order to fix this issue upstream we've opened this issue: /Users/abpostelnicu/Projects/llvm/llvm/tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py If that change gets accepted most likely it will land in 7.0 and we are currently a little bit behind with clang-tidy, at 5.0.1, thus we need an in-tree patch for our tool-chain build.
Bug 1478644 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
In order to perform static-analysis on Gecko we use the clang-tidy infrastructure, for this we leverage a tool run-clang-tidy, that spawns multiple process in order for the analysis process to be faster. Unfortunately run-clang-tidy doesn't uses a write synchronization when it comes to dump output in the stdout of stderr, because of this many time we see that the outputs is interlaced with results from different files, thus making it less readable to human and also to machine. In order to fix this issue upstream we've opened this issue: /Users/abpostelnicu/Projects/llvm/llvm/tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py If that change gets accepted most likely it will land in 7.0 and we are currently a little bit behind with clang-tidy, at 5.0.1, thus we need an in-tree patch for our tool-chain build.